Replace ignore_indices with 3 other options
#4436
Assignees
Labels
Comments
ghost
assigned
martijnvg
added a commit
to martijnvg/elasticsearch
that referenced
this issue
Dec 16, 2013
…` and `allow_no_indices`. * `ignore_unavailable` - Controls whether to ignore if any specified indices are unavailable, this includes indices that don't exist or closed indices. Either `true` or `false` can be specified. * `allow_no_indices` - Controls whether to fail if a wildcard indices expressions results into no concrete indices. Either `true` or `false` can be specified. For example if the wildcard expression `foo*` is specified and no indices are available that start with `foo` then depending on this setting the request will fail. This setting is also applicable when `_all`, `*` or no index has been specified. * `expand_wildcards` - Controls to what kind of concrete indices wildcard indices expression expand to. If `open` is specified then the wildcard expression if expanded to only open indices and if `closed` is specified then the wildcard expression if expanded only to closed indices. Also both values (`open,closed`) can be specified to expand to all indices. Relates to elastic#4436
martijnvg
added a commit
that referenced
this issue
Jan 2, 2014
…s` and `allow_no_indices`. * `ignore_unavailable` - Controls whether to ignore if any specified indices are unavailable, this includes indices that don't exist or closed indices. Either `true` or `false` can be specified. * `allow_no_indices` - Controls whether to fail if a wildcard indices expressions results into no concrete indices. Either `true` or `false` can be specified. For example if the wildcard expression `foo*` is specified and no indices are available that start with `foo` then depending on this setting the request will fail. This setting is also applicable when `_all`, `*` or no index has been specified. * `expand_wildcards` - Controls to what kind of concrete indices wildcard indices expression expand to. If `open` is specified then the wildcard expression if expanded to only open indices and if `closed` is specified then the wildcard expression if expanded only to closed indices. Also both values (`open,closed`) can be specified to expand to all indices. Closes to #4436
|
Closed via: f4bf0d5 |
honzakral
added a commit
to elastic/elasticsearch-py
that referenced
this issue
Jan 2, 2014
See elastic/elasticsearch#4436 for more details
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Jan 12, 2014
…Index Settings" APIs * prefix * ignore_indices * ignore_unavailable * allow_no_indices * expand_wildcards * flat_settings Related: elastic/elasticsearch#4436, elastic/elasticsearch#4453
brusic
pushed a commit
to brusic/elasticsearch
that referenced
this issue
Jan 19, 2014
…s` and `allow_no_indices`. * `ignore_unavailable` - Controls whether to ignore if any specified indices are unavailable, this includes indices that don't exist or closed indices. Either `true` or `false` can be specified. * `allow_no_indices` - Controls whether to fail if a wildcard indices expressions results into no concrete indices. Either `true` or `false` can be specified. For example if the wildcard expression `foo*` is specified and no indices are available that start with `foo` then depending on this setting the request will fail. This setting is also applicable when `_all`, `*` or no index has been specified. * `expand_wildcards` - Controls to what kind of concrete indices wildcard indices expression expand to. If `open` is specified then the wildcard expression if expanded to only open indices and if `closed` is specified then the wildcard expression if expanded only to closed indices. Also both values (`open,closed`) can be specified to expand to all indices. Closes to elastic#4436
karmi
added a commit
to elastic/elasticsearch-ruby
that referenced
this issue
Mar 13, 2014
rciorba
added a commit
to rciorba/elasticsearch-py
that referenced
this issue
Mar 2, 2018
See elastic/elasticsearch#4436 for more details
riki-tanaka
added a commit
to riki-tanaka/ElasticSearch-Python
that referenced
this issue
Jun 17, 2021
See elastic/elasticsearch#4436 for more details
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Today the
ignore_indicesoption controls what to do when an specified index doesn't exists.The new following options will replace
ignore_indicesto make ignoring indices more flexible:ignore_unavailable- Controls whether to ignore specified indices that are unavailable. Unavailable refers to indices that don't exist or are closed.expand_wildcards- Controls what kind of indices should be expanded with wildcard expressions. Ifopenis specified a wildcard expression expands only into open indices and ifclosedis specified a wildcard expression only expands into closed indices. The latter only makes sense in the close index api, which it will default to.allow_no_indices- Controls whether it is allowed that a wildcard expression expands into zero concrete indices. This option also applies when_allor no index has been specified.The text was updated successfully, but these errors were encountered: